Skip to main content

This is a new service – your feedback will help us to improve it.

Your data has issues

There is a problem

  • point column must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Felled date Entry date Start date End date
027STAA003 TPO027STA

Unexpected geom type

2025-09-09
192G001 TPO192

Unexpected geom type

2025-09-09
192G003 TPO192

Unexpected geom type

2025-09-09
192G004 TPO192

Unexpected geom type

2025-09-09
192G005 TPO192

Unexpected geom type

2025-09-09
192G002 TPO192

Unexpected geom type

2025-09-09
192G006 TPO192

Unexpected geom type

2025-09-09
190A001 TPO190

Unexpected geom type

2025-09-09
189G001 TPO189

Unexpected geom type

2025-09-09
187G001 TPO187

Unexpected geom type

2025-09-09
187G002 TPO187

Unexpected geom type

2025-09-09
186G001 TPO186

Unexpected geom type

2025-09-09
186G002 TPO186

Unexpected geom type

2025-09-09
186G003 TPO186

Unexpected geom type

2025-09-09
186G004 TPO186

Unexpected geom type

2025-09-09
183G001 TPO183

Unexpected geom type

2025-09-09
183G002 TPO183

Unexpected geom type

2025-09-09
129G001 TPO129

Unexpected geom type

2025-09-09
129G002 TPO129

Unexpected geom type

2025-09-09
124G001 TPO124

Unexpected geom type

2025-09-09
124G002 TPO124

Unexpected geom type

2025-09-09
121G001 TPO121

Unexpected geom type

2025-09-09
119G001 TPO119

Unexpected geom type

1 Prunus Felled 2025-09-09
118A001 TPO118

Unexpected geom type

2025-09-09
114G001 TPO114

Unexpected geom type

2025-09-09
114G002 TPO114

Unexpected geom type

2025-09-09
094G001 TPO094

Unexpected geom type

2025-09-09
089G001 TPO089

Unexpected geom type

2025-09-09
089G002 TPO089

Unexpected geom type

2025-09-09
005STAA001 TPO005STA

Unexpected geom type

2025-09-09
005STAA002 TPO005STA

Unexpected geom type

2025-09-09
005STAA003 TPO005STA

Unexpected geom type

2025-09-09
005STAA004 TPO005STA

Unexpected geom type

2025-09-09
005STAA005 TPO005STA

Unexpected geom type

2025-09-09
005STAG001 TPO005STA

Unexpected geom type

2025-09-09
005STAG002 TPO005STA

Unexpected geom type

2025-09-09
005STAG003 TPO005STA

Unexpected geom type

2025-09-09
005STAG004 TPO005STA

Unexpected geom type

2025-09-09
005STAG005 TPO005STA

Unexpected geom type

2025-09-09
005STAG006 TPO005STA

Unexpected geom type

2025-09-09
005STAG007 TPO005STA

Unexpected geom type

2025-09-09
005STAG008 TPO005STA

Unexpected geom type

2025-09-09
005STAG009 TPO005STA

Unexpected geom type

2025-09-09
005STAG010 TPO005STA

Unexpected geom type

2025-09-09
005STAG011 TPO005STA

Unexpected geom type

2025-09-09
184G001 TPO184

Unexpected geom type

2025-09-09
184G002 TPO184

Unexpected geom type

2025-09-09
170A001 TPO170

Unexpected geom type

2025-09-09
166A001 TPO166

Unexpected geom type

2025-09-09
162G001 TPO162

Unexpected geom type

2025-09-09

Showing rows 201 to 250 of 300

How to fix this issue

Your dataset is missing the point column.

The Tree guidance explains how to fix the issue:

point

The approximate location of the centre of the tree.

You must provide a point or geometry for each tree. You may provide both.

The point must be in the WGS84 coordinate reference system. If you’re providing point in a CSV, geometry should be in well-known text (WKT).

Example: POINT (-0.681152 52.762892)

If you’re providing point in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Spelthorne Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL